Skip to content

chore(release): 1.126.04312 (vscode 1.126.0)#24

Open
github-actions[bot] wants to merge 1 commit into
mainfrom
release/1.126.04312
Open

chore(release): 1.126.04312 (vscode 1.126.0)#24
github-actions[bot] wants to merge 1 commit into
mainfrom
release/1.126.04312

Conversation

@github-actions

Copy link
Copy Markdown
Contributor

Auto-generated release PR — the build already succeeded and the
GitHub Release is already published with signed, notarized artifacts.
Merging this PR advances main's pinned upstream version and points
the in-app auto-updater at the new ZIP.

Artifact verification

  • DMG SHA-256: 75886f7fc3107d9c5aacdcddec7fdd951fa91779af409c7ba4ba5ec79d49a152
  • ZIP SHA-256: f6d62a61eb2cb12cffb2bf3d2fc27eb3c22eae41092d7a6eaa9901769e7da1d9

What happens on merge

  • upstream/stable.json advances to track 1.126.0.
  • versions/stable/darwin-arm64/latest.json points at the new
    ZIP; the in-app auto-updater (Squirrel.Mac) picks it up on its
    next poll.

Why the build status check is missing

The build job on this PR is skipped — the same version was just
built and notarized in run 28328710988 above. The skip is
gated by the auto-release label; see the build job if: in
.github/workflows/cron-build-and-release.yml.

@github-actions github-actions Bot added the auto-release Cron release PR; safe to merge once you've reviewed label Jun 28, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

auto-release Cron release PR; safe to merge once you've reviewed

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants